System and Method for Securing Secure Memory Allocations in an Information Handling System

ABSTRACT

An information handling system has a secure data storage partition allocation. Access to the secure storage partition is limited to a set of authorized functions authorized to access the secure storage partition. The authorization of a function may be determined by a unique identification corresponding to the function or a reverse trace.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to information handling systems, and more particularly relates to securing data storage allocations in an information handling system.

BACKGROUND

As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option is an information handling system. An information handling system generally processes, compiles, stores, or communicates information or data for business, personal, or other purposes. Technology and information handling needs and requirements can vary between different applications. Thus information handling systems can also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information can be processed, stored, or communicated. The variations in information handling systems allow information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems can include a variety of hardware and software resources that can be configured to process, store, and communicate information and can include one or more computer systems, graphics interface systems, data storage systems, networking systems, and mobile communication systems. Information handling systems can also implement various virtualized architectures. Data and voice communications among information handling systems may be via networks that are wired, wireless, or some combination.

SUMMARY

An information handling system may have allocated a secure storage partition. Access to the secure storage partition is limited to a set of functions authorized to access the secure storage partition. The authorization of a function may be verified by a unique identification or reverse trace.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the Figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings herein, in which:

FIG. 1 is a block diagram illustrating an information handling system according to an embodiment of the present disclosure;

FIG. 2 is a block diagram illustrating a structure of a software stack according to an embodiment of the present disclosure;

FIG. 3 is a flow diagram illustrating a method of registration for secure storage;

FIG. 4 is a flow diagram illustrating a method for securing storage;

FIG. 5 is a block diagram illustrating a structure of a secure storage access function according to an embodiment of the present disclosure;

FIG. 6 is a flow diagram illustrating a method of operation of a secure storage access function according to an embodiment of the present disclosure; and

FIG. 7 is a flow diagram illustrating a method of parsing a command involving secure storage into a set of commands.

The use of the same reference symbols in different drawings indicates similar or identical items.

DETAILED DESCRIPTION OF THE DRAWINGS

The following description in combination with the Figures is provided to assist in understanding the teachings disclosed herein. The description is focused on specific implementations and embodiments of the teachings, and is provided to assist in describing the teachings. This focus should not be interpreted as a limitation on the scope or applicability of the teachings.

An information handing system may include a motherboard that in turn may comprise components such as a data storage and a processor to perform computations. The processor may run BIOS software and operating system software. The BIOS software may be firmware based and perform hardware, for example, motherboard hardware, initialization during booting of the processor. The operating system may be system software that manages motherboard hardware and software resources and provides common services for computer programs. In embodiments, the Unified Extensible Firmware Interface (UEFI) may subsume the BIOS or BIOS functionality.

The information handling system may include storage. For example, the motherboard may have data storage for storing data. The storage may be partitioned into secure and unsecure partitions. It may be desirable to control access to the secure partitions for security such that an unauthorized function or routine may be proscribed from accessing the secure partitions by preventing access to the secure partitions by the unauthorized function or routine. An example of such a storage may be flash memory located on the motherboard to provide data storage for use by the motherboard and components thereof such as a motherboard processor. In a particular embodiment, the storage may be allocated as Universal Serial Bus (USB) partitions.

A manufacturer or producer, such as an Original Equipment Manufacturer (OEM), of the information handling system may desire that a limited and authorized subset of functions, routines and computer programs may access the secure storage partition. For example, the manufacturer may desire that access to the secure storage partitions is limited to authorized functions because the secure storage partitions may be used for boot-up and operation of the information handling system. As would be understood by one of skill in the art, the information handling system may be loaded with various programs and functions from diverse sources. Furthermore, the information handling system may be connected to the internet such that the information handing system is internet-exposed to programs and functions operating over the internet. To ensure the security of the secure storage partitions, it is desirable to control and exclude various programs and functions from accessing the secure partitions.

In one embodiment, when a driver or function is installed on an information handling system, it is given a unique identification. Then the driver or function is registered with the information handling system with its unique identification. The information handling system has a set of authorized unique identifications representing drivers or functions which are authorized to access the secure storage partitions. If it is desired that the registering driver or function have access to the secure partitions, then the unique identification corresponding to the registering driver or function will be added to the set of authorized unique identifications representing drivers or functions which are authorized to access the secure storage partitions.

When a driver or function attempts to access the secure storage partitions, the unique identification corresponding to the driver or function attempting to access the secure storage partitions will be compared with the set of authorized unique identifications representing drivers or functions which are authorized to access the secure storage partitions. If the driver or function is authorized based on the unique identifier, the function or driver will be able to access the secure storage partitions; if the driver or function is not authorized, the function or driver will be unable to access the secure storage partitions.

In an alternate embodiment, in response to a function call to access the secure storage, a reverse trace is executed to determine if the calling function is authorized to access the secure storage; if the function is authorized to access the secure storage, the function may access the secure partition; if the function is unauthorized, the function is denied access to the secure partition. For example, the reverse trace may be used to determine whether the function call is by a proscribed program or function or by an authorized program or function which is authorized to access the secure partition. In embodiments, the results of the reverse trace may be used to determine that the function call is by an authorized program or function by determining the location, for example, in memory, from which the function call originates. When it is determined that the function call is by an authorized program or function, the function call then accesses the secure memory according to the function call. If, however, an authorized program or function fails to be verified as authorized to access the secure memory, the function call is prevented from accessing the secure memory.

More particularly, in embodiments, the manufacturer or producer, for example, the OEM, of the information handling system may implement a function or a set of functions which may be utilized by the information handling system, and this set of functions may be considered a set of proprietary functions. The set of proprietary functions may include an access function to a secure storage partition. This access function may be invoked by another function of the set of proprietary functions. The access function may include reverse trace functionality which may be a further function call such as a reverse trace function. The reverse trace functionality may reverse trace the origin of the function call and may determine a location, a program, or a function from which the access function is asserted. The information handling system may include an authorized list which lists programs and functions which are authorized to be permitted to access the secure storage partition.

FIG. 1 illustrates a generalized embodiment of information handling system 100. For purpose of this disclosure information handling system 100 can include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, information handling system 100 can be a personal computer, a desktop computer, a laptop computer, a smart phone, a tablet device or other consumer electronic device, a network server, a network storage device, a switch router or other network communication device, or any other computing device and may vary in size, shape, performance, functionality, and price. Information handling system 100 may be connectable to the internet (not shown).

Information handling system 100 includes a motherboard 110, and may also include other components such as a display or input/output (I/O) devices or components such as a keyboard (not shown). Motherboard 110 includes a processor 112, a data storage 114, and computing elements 116. Computing elements 116 may comprise multiple computing elements such as subsidiary motherboard processors. Motherboard 110 may include other components and drivers not shown. In addition, motherboard 110 includes one or more busses coupling processor 112 with storage 114 and may include one or more busses connecting storage 114 with one or more elements of computing elements 116. Thus, processor 112 may access storage 114 and one or more elements of computing elements 116 may access storage 114.

Storage 114 is allocated or partitioned into a unsecure storage partition 122 and a secure storage partition 124. In embodiments, storage 114 comprises flash memory and as such is an electronic (solid-state) non-volatile computer storage medium that can be electrically erased and reprogrammed. Storage 114 may be allocated as USB partitions and some of these partitions may form secure storage partition 124.

In operation of information handling system 100, processor 112 may operate or function as a host and computing elements 116 may operate or function as a server on motherboard 110 such as, for example, an integrated Remote Access Controller providing a Lifecycle Controller to the motherboard which simplifies server lifecycle management tasks like provisioning, deployment, servicing, user customization, patching and updating. Lifecycle drivers run on computing elements 116 provide a collection of out-of-band automation services, embedded pre-OS applications, and remote interfaces.

When processor 112 operates or functions as a host of motherboard 110, processor 112 may run or execute a BIOS and operating system. The BIOS may be involved in booting information handling system 100.

FIG. 2 shows a software stack 200 that may run on processor 112 of FIG. 1. Software stack 200 includes operating system 210, and BIOS 230. Operating system 210 may interface with application programs. BIOS 230 may be part of or subsumed into the UEFI protocol. BIOS 230 operates at the firmware level above the hardware level of the processor executing BIOS 230, for example processor 112 of FIG. 1. BIOS 230 may execute a pre-boot verify upon booting of the associated information handling system and may execute diverse drivers upon start-up and be internet exposed if the associated information handling system is connected to the internet. Thus, software stack 200 may be exposed to diverse drivers and functions outside of OEM control.

Returning to FIG. 1, to ensure the security of secure storage partition 124 it may be desirable to ensure that access to secure storage partition 124 is limited to a set or subset of authorized drivers and functions. Other drivers and functions may be prevented from accessing or denied access to secure storage partition 124 such that access to secure storage partition 124 is limited to the set of authorized drivers and functions exclusive of other drivers and functions, which may be referred to as unauthorized drivers and functions. Thus, unauthorized drivers and functions are prevented from accessing secure storage partition 124.

In embodiments, to limit access to secure memory partition 124 to authorized drivers and functions, a registration process may be used to provide access to secure memory partition 124 by authorized drivers and functions and to proscribe unauthorized drivers and functions from accessing secure memory partition 124.

FIG. 3 shows a registration process 300. At 301, the process begins with the installation of a function or driver in information handling system 100. This may be a temporary installation, such as a temporary download or saving of a function to memory, from which the function will be subsequently removed, for example, by over-writing. At 305, the installed function or driver is assigned a unique identification representing the installed function or driver. At 310, the installed function or driver is registered, for example, with information handling system 100 by the assigned unique identification representing the installed function or driver.

At 320, it is determined if the installed function or driver is to be allowed access to secure memory partition 124. If the function or driver is proscribed from access to secure memory partition 124, at 322, the unique identification representing the installed function or driver is not added to an authorized set of unique identifications representing functions and allowed access to secure memory partition 124. If the function or driver is to have access to secure memory partition 124, at 324, the unique identification representing the installed function or driver is added to an authorized set of unique identifications representing functions and allowed access to secure memory partition 124.

In embodiments, the set of unique identifications representing the drivers and functions authorized to access secure storage partition 124 may be maintained as a list of unique identifications by computing elements 116, and more specifically, the Lifecycle Controller running on computing elements 116.

FIG. 4 shows a method 400 for securing storage. At 401, a request is received to access secure storage. At 410, the unique identification representing the requesting function or driver is compared with the set of unique identifications representing the drivers and functions authorized to access secure storage partition 124. If the unique identification of the requesting function or driver is not enunciated in the set of unique identifications representing authorized drivers and functions, then at 412, the request to access secure storage will be denied such that the requesting function will be blocked from accessing secure storage partition 124. If, however, the unique identification of the requesting function or driver is enunciated in the set of unique identifications representing authorized drivers and functions, then at 414, the request to access secure storage will be allowed such that the requesting function will access secure storage partition 124.

In embodiments, the unique identification may be allocated as a private key in a private/public key security protocol.

In further embodiments, to limit access to secure memory partition 124 to authorized drivers and functions, a proprietary driver or function may be provided by the OEM of the information handling system 100 and motherboard 110 for accessing secure storage partition 124. Such a proprietary driver may be referred to as a secure storage partition access function. This secure storage partition access function may access secure storage partition 124. Invocation of the secure storage partition access function may be limited to authorized drivers and functions authorized to access secure storage partition 124. Access to secure storage partition 124 is limited to the secure storage partition access function or authorized drivers and functions invoking the same such that other drivers or functions are prevented from accessing secure storage partition 124.

Information handling system 100 may maintain a list of the authorized drivers and functions authorized to access secure storage partition 124. Invocation of the secure storage partition access function may be limited to the authorized drivers and functions in this list of the authorized drivers and functions authorized to access secure storage partition 124, thereby limiting access to secure storage partition 124 to these authorized drivers and functions. In embodiments, the list of the authorized drivers and functions authorized to access secure storage partition 124 may be maintained by computing elements 116, and more specifically, the Lifecycle Controller running on computing elements 116.

To the end of limiting invocation of the secure storage partition access function to the authorized drivers and functions authorized to access secure storage partition 124, the secure storage partition access function may include reverse trace functionality which may confirm or ensure that the secure storage partition access function is invoked by authorized drivers and functions authorized to access secure storage partition 124 from the list of authorized drivers and functions authorized to access secure storage partition 124.

FIG. 5 illustrates the structure of a secure storage partition access function 500. Secure storage partition access function 500 includes reverse trace function 510 and storage access function 520. When secure storage partition access function 500 is invoked by a program, function, or driver, prior to execution of storage access function 520, reverse trace function 510 is executed. Reverse trace function 510 reverse traces the program, function, or driver invoking secure storage partition access function 500 to determine the program, function, or driver invoking secure storage partition access function 500. Secure storage partition access function 300 then determines if the determined program, function, or driver is authorized to access secure storage partition 124 by comparing the determined program, function, or driver with the list of authorized drivers and functions authorized to access secure storage partition 124. If the program, function, or driver invoking secure storage partition access function 500 is on the list and thus authorized to access secure storage partition 124, then storage access function 520 is executed, thereby accessing secure storage partition 124. If the program, function, or driver invoking secure storage partition access function 500 is not on the list and is thus precluded from accessing secure storage partition 124, then storage access function 520 is not executed, and secure storage partition access function 500 fails to access secure storage partition 124.

In embodiments, reverse trace function 510 may determine the program, function, or driver invoking secure storage partition access function 500 by reverse tracing the location of the program, function, or driver invoking secure storage partition access function 500. If the location of the program, function, or driver indicates that the program, function, or driver is not on the list of authorized drivers and functions authorized to access secure storage partition 124, then reverse trace function 510 determines the program, function, or driver invoking secure storage partition access function 500 is not authorized to access secure storage partition 124. If however, the invocation of secure storage partition access function 500 originates from a secure location, then reverse trace function 510 determines the program, function, or driver invoking secure storage partition access function 500 is authorized to access secure storage partition 124.

FIG. 6 is a flowchart 600 of an embodiment of operation of secure storage partition access function 500. At 601, secure storage partition access function 500 is invoked. At 605, secure storage partition access function 500 performs a reverse trace to determine the invoking function. For example, the reverse trace may determine a location of the invoking function so that the invoking program, function, or driver may be determined. At 610 it is determined if the invoking function is an authorized function. For example, the determined invoking program, function, or driver may be compared to a list of authorized functions and drivers authorized to access secure storage partition 124. If it is determined that the determined invoking program, function, or driver is not an authorized function, then at 612, secure storage partition access function 500 returns memory access failure such that the invoking function will be blocked from accessing secure storage partition 124. If, however, it is determined that the determined invoking program, function, or driver is an authorized function, then at 614, secure storage partition access function 500 accesses secure storage partition 124.

In implementations, secure storage partition access function 500 is a BIOS level command or function. Thus, secure storage partition access function 500 may be a firmware command or function implemented at the lowest software level above the hardware level. Secure storage partition access function 500 may be the sole and unique command for accessing the secure storage such that authorized functions use secure storage partition access function 500 to access secure storage. A higher level function or command may be parsed as it traverses lower levels for implementation and if the higher level function or command involves accessing the secure storage, then the higher level function or command may be parsed as it traverses the software stack into a set of lower level commands comprising secure storage partition access function 500.

Furthermore, because secure storage partition access function 500 is a BIOS level command or function with sole access to the secure storage, access to the secure storage cannot be obtained by a higher level program, function, or driver invoking a BIOS level access command to access the secure storage. That is, use of secure storage partition access function 500 to access the secure storage cannot be circumvented.

FIG. 7 is a flowchart 700 of an embodiment of parsing a command into a set of commands including a secure storage partition access function at the BIOS level. At 710, a file system level command, function, or driver is invoked. The invoked file system level command, function, or driver involves accessing secure storage. At 720, the invoked file system level command, function, or driver is translated into a set of commands at the disk level. Disk level commands are at the BIOS level above the hardware level and implemented by firmware. At 710, the disk level commands are further parsed into a set of commands at the block level. Block level commands are at the BIOS level above the hardware level and implemented by firmware. The set of commands at the block level will include a call to secure storage partition access function 500 because the parsed file system level command, function, or driver involved accessing secure storage. As would be understood by one of skill in the art, because secure storage partition access function 500 is at the BIOS level above the hardware level, access to the secure storage cannot be circumvented by using low level firmware commands to access the secure storage.

While in the above, a secure storage access function is described at the block level, a secure storage access function may be implemented at any level in BIOS from the file system level to the block level.

Devices, modules, resources, or programs that are in communication with one another need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices, modules, resources, or programs that are in communication with one another can communicate directly or indirectly through one or more intermediaries.

Although only a few exemplary embodiments have been described in detail herein, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of the embodiments of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of the embodiments of the present disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures. 

What is claimed is:
 1. An information handling system comprising: a processor; a data storage partitioned to include a secure storage partition; a set of authorized functions authorized to access the secure storage partition; and a secure storage access function operable to access the secure storage partition, wherein the secure storage access function has reverse trace functionality to determine if an invoking function invoking the secure storage access function is an authorized function of the set of authorized functions.
 2. The information handling system of claim 1, wherein the secure storage access function is a BIOS level command.
 3. The information handling system of claim 1, wherein the reverse trace functionality reverse traces a location of the invoking function to determine if the invoking function is an authorized function.
 4. The information handling system of claim 1, wherein the invoking function is determined by reverse tracing the invoking function to determine the invoking function and wherein the determined invoking function is compared to a list of authorized functions to determine if the invoking function is an authorized function.
 5. The information handling system of claim 1, further comprising a list of authorized functions.
 6. The information handling system of claim 5, further comprising computing elements operable to run a lifecycle controller for the information system, wherein the lifecycle controller maintains the list of authorized functions.
 7. The information handling system of claim 1, wherein the secure storage access function is provided by the OEM of the information handling system.
 8. A method performed in an information handling system having a data storage partitioned into a secure storage partition, the method comprising: receiving an invocation of a secure storage partition access function to access the secure storage partition; reverse tracing the invocation to determine an invoking function invoking the secure storage partition access function; determining if the invoking function is an authorized function authorized to access the secure storage partition; and if the invoking function is an authorized function, accessing the secure storage partition via the secure storage partition access function.
 9. The method of claim 8, further comprising: if the invoking function is not an authorized function, failing to access the secure storage partition.
 10. The method of claim 8, wherein the secure storage partition access function is a BIOS level command.
 11. The method of claim 8, wherein reverse tracing the invoking function comprises determining a location of the invoking function.
 12. The method of claim 11, wherein determining if the invoking function is an authorized function comprises comparing the invoking function with a list of authorized functions.
 13. The method of claim 8, wherein a list of authorized functions is maintained by the information handling system.
 14. A method performed in an information handling system having a data storage partitioned into a secure storage partition, the method comprising: installing a function; assigning a unique identification to the installed function; registering the installed function with the information handling system using the unique identification; determining if the registered function is to have access to the secure storage partition; and if the invoking function is to have access to the secure storage partition, adding the unique identification to a set of unique identifications representing functions authorized to access to the secure storage partition.
 15. The method of claim 14, wherein if the invoking function is to be denied access to the secure storage partition, failing to add the unique identification to the set of unique identifications representing functions authorized to access to the secure storage partition.
 16. The method of claim 14, wherein a lifecycle controller of the information handling system maintains a list of the set of unique identifications representing functions authorized to access to the secure storage partition.
 17. The method of claim 14, wherein the unique identification is allocated as private/public key pair.
 18. The method of claim 14, further comprising: receiving a request to access the secure storage partition from a requesting function; determining a requestor unique identification of the requesting function; comparing the requestor unique identification with the unique identifications of the set of unique identifications; and if the requestor unique identification matches a unique identification of the set of unique identifications, allowing the requesting function to access the secure storage partition.
 19. The method of claim 18, wherein if the requestor unique identification fails to match a unique identification of the set of unique identifications, denying the requesting function access to the secure storage partition.
 20. The method of claim 18, wherein a lifecycle controller of the information handling system performs the comparing the requestor unique identification with the unique identifications of the set of unique identifications. 